SPR

Technote

Problem:
This issue was reported to Quality Engineering and was addressed in Notes 5.0.6
Client. The issue regressed in Notes 6.x which was reported to Quality
Engineering as SPR# AMOR6JT5JH / APAR# LO11509 and was fixed in Notes 6.5.6.
The issue is currently under investigation for a fix in future Notes 7.x
releases.

Excerpt from the Lotus Notes and Domino Release 6.5.6 MR fix list (available at
http://www.ibm.com/developerworks/lotus):

Design
SPR# AMOR6JT5JH - Prior to this fix, an embedded view with a single category
jumped to another category without user's intervention, when the database on a
server was updated by other users.

Excerpt from the Lotus Notes and Lotus Domino Release 5.0.6 QMR fix list:

Design - Embedded Element - View
SPR# GFLY4MRJNA - Fixed a problem where the correct documents were not
displayed in an embedded view when a new category above it was created. The
embedded view was using a restricted category.

Refer to the Upgrade Central site for details on upgrading Notes/Domino.


Workarounds
There are 2 ways to avoid this issue.

Note: The workarounds will not resolve the scenario where, if the specified
category does not have any matching entries then a partial match category will
be returned. For example, if the view is set to show category "DocA" and there
are no such entries, but there are entries for "DocB" then these entries will
be displayed in the view. This issue is described in the following document:
"Unexpected Category displays when using Show Single Category Embedded View"
(#1108324).

Change the embedded view so that it doesn't refresh automatically
If the view is necessary for the user interface then have one view available
via the user interface that refreshes automatically, and have a second view
which is hidden and does not refresh automatically. A view's refresh setting
"On Refresh" is found on the Info ("i") tab. The property can be set to
"Display Indicator" to disable automatic refreshing.

OR

Refresh the document, either manually or automatically
You can manually refresh a document opened in Edit mode via the F9 key, or by
calling Formula or LotusScript code within a button, action or field event.
The @Command function ViewRefreshFields and the LotusScript Refresh method (of
the NotesUIDocument class) can be used to refresh a document opened in Edit
mode.

For cases where the view is embedded within a Form design an automated
workaround which does not require user interaction can also be coded using
LotusScript. This method works whether the document is Edit mode or Read
mode. The NotesTimer class can be used to periodically call a subroutine which
refreshes the document using the Refresh method.

This is accomplished by adding code to the Form's PostOpen and Declarations
events (the code does not need to be in the Globals events). Note: When the
subroutine code for ReviewView is pasted into the Declarations section it will
automatically become an individual subroutine for the Form; this is expected.

Note: It is recommended that the timer refresh interval not be set to 1 second
as this may cause undesired performance issues. It is best to initially set
the interval from 5 to 10 seconds. If the addition and deletion of categories
is frequent enough to still cause unexpected behavior then decrease the
interval.

(Declarations)
Dim viewTimer As NotesTimer
Dim ws As NotesUIWorkspace
Sub refreshView(Source As NotesTimer)
ws.ViewRefresh
End Sub

Postopen
Set ws = New NotesUIWorkspace
Set viewTimer = New NotesTimer(5)
On Event Alarm From viewTimer Call refreshView
More >